chore: upgrade surrealdb package to v1.0.0 - #1507
Conversation
|
🚀 Dogfood this PR with:
curl -fsSL https://raw.githubusercontent.com/CommunityToolkit/Aspire/main/eng/scripts/dogfood-pr.sh | bash -s -- 1507Or
iex "& { $(irm https://raw.githubusercontent.com/CommunityToolkit/Aspire/main/eng/scripts/dogfood-pr.ps1) } 1507" |
| <ItemGroup> | ||
| <PackageReference Include="Bogus" /> | ||
| <PackageReference Include="Microsoft.AspNetCore.OpenApi" /> | ||
| <PackageReference Include="Microsoft.AspNetCore.OpenApi" VersionOverride="10.0.10" /> |
There was a problem hiding this comment.
Is there a reason that we wouldn't bump this in the Directory.Packages.props? If we start using VersionOverrides it becomes a problem trying to keep on top of where versions are coming from (I do acknowledge that this is in the examples project, but once a pattern starts somewhere it spreads).
There was a problem hiding this comment.
I did not want to break the other projects just to upgrade mine. I think there must be a plan to upgrade packages at some point. I can do another PR after to deal with that if you want.
There was a problem hiding this comment.
Is there a need to bump it? Or do we end up with transient dependency collisions if it's not updated?
2 participants
PR Checklist
Other information